-
Notifications
You must be signed in to change notification settings - Fork 3.9k
server: add EngineStats endpoint in multitenant setup #143633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left some minor comments above. The rest of the PR looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a couple of comments. Otherwise it looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a couple of comments. Otherwise it looks good.
4f26617
to
9842bc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
EngineStats endpoint was inaccessible from secondary tenant. EngineStats endpoint provides statistics of storage layer which can help diagnose myriad of issues critical to database performance. To address this, we created EngineStatus endpoint in tenant status server. Implementation uses tenant connector to redirect call to system status server on requested kv node. Access to this endpoint is guarded by `can_view_node_info` capability as this endpoint returns info of all stores on a given node. Updated corresponding unit tests. Epic: CRDB-38968 Fixes: cockroachdb#110020 Part of: CRDB-31226 Release note: None
bors r=shubhamdhama,cthumuluru-crdb |
👎 Rejected by code reviews |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you!
bors r=shubhamdhama,cthumuluru-crdb |
Build succeeded: |
EngineStats endpoint was inaccessible from secondary tenant.
EngineStats endpoint provides statistics of storage layer which can help diagnose myriad of issues critical to database performance.
To address this, we created EngineStatus endpoint in tenant status server. Implementation uses tenant connector to redirect call to system status server on requested kv node. Access to this endpoint is guarded by
can_view_node_info
capability as this endpoint returns info of all stores on a given node. Updated corresponding unit tests.Epic: CRDB-38968
Fixes: #110020
Release note: None